‫System commands are related to the operations performed on the operating system in the target computer.
‫We've used almost all of the commands seen on the slide before, but I want to remind you of where we
‫will use the command clear that clears the event logs for Windows Systems.
‫It clears application system and security files.
‫We use the command interpreter against Windows Systems Lecture.
‫Execute runs a command on the victim machine.
‫We used it to create a channel to have a command show on the victim machine.
‫Get PIDE shows the idea of the process in which our interpreter session is injected.
‫Get you I.D. to see which privileges we have at the moment, we use this and get PID commands while
‫demonstrating the migration.
‫Kill terminates the specified process on the victim.
‫I don't think we've used that one yet.
‫P.S. lists, the process is running on the victim.
‫We use that to find a process to migrate.
‫Reboot, reboots the victim system.
‫That means you'll lose this session, but we've rebooted the victim machine while demonstrating persistence.
‫Shutdown is just that it shuts the victim machine down.
‫That means, again, you'll lose the current session, Regg, to manage the registry of the victim system.
‫We use this command while removing the back door, if you remember.
‫Shell to have a command shell on the victim.
‫I remember that we used this command in the session management lecturer.
‫This info, well, it's just that it's the command that I use most throughout the course, it gets information
‫about the victim machine, such as the operating system.
‫So let's have a look at the system command in action.
‫Here I have an interpreter session in Colly Disinfo to gather information about the victim system,
‫and I can see the operating system, the architecture domain name of the computer logged on user.
‫No.
‫Get pide, see the process ID, we are injected and that's ninety-six for.
‫Get you ID to see who we are on the victim machine and we are the system user, which is very good for
‫us.
‫He has to list the running processes and here's our process, nine six.
‫Now we can use the kill command to kill any process, so let's kill one one eight nine two.
‫All right, let's the process again, peace and the process 192 doesn't exist anymore.
‫Let's kill another one, whatever.
‫Shell to obtain a shell on the victim.
‫Control see to exit from the show by turning in.
‫So what else?
‫Clear left to clear the locks.
‫So let's go to the victim before running the command over the event viewer and see all the log files.
‫Back to Cali and run the clear command.
‫And Windows XP, refresh the event viewer and the logs have gone.
‫Execute to run a command on the victim system.
‫Let's run the command EXI, which opens a command prompt F to specify the file to be executed, ie to
‫interact with a created channel.
‫Now look at that.
‫The channel created and we are on the same channel.
‫So that means we have a command shell on the victim machine in an alternative way.
‫Now you can use control C to terminate the channel.
‫I kept the shut down command to the end because, well, it will shut down the victim system.
‫But look at this, I run the command and as you see, the victim system is shutting down.
‫Wollar.